Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
Successful and unsuccessful logins and logouts must be logged.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-765 | GEN000440 | SV-63363r1_rule | ECAR-1 ECAR-2 ECAR-3 | Medium |
| Description |
|---|
| Monitoring and recording successful and unsuccessful logins assists in tracking unauthorized access to the system. Without this logging, the ability to track unauthorized activity to specific user accounts may be diminished. |
| STIG | Date |
|---|---|
| Oracle Linux 5 Security Technical Implementation Guide | 2015-03-26 |
Details
| Check Text ( C-52075r1_chk ) |
|---|
| Determine if all logon attempts are being logged. Procedure: Verify successful logins are being logged: # last -R | more If the command does not return successful logins, this is a finding. Verify if unsuccessful logons are being logged: # lastb -R | more If the command does not return unsuccessful logins, this is a finding. |
| Fix Text (F-53961r1_fix) |
|---|
| Make sure the collection files exist. Procedure: If there are no successful logins being returned from the "last" command, create /var/log/wtmp: # touch /var/log/wtmp If there are no unsuccessful logins being returned from the "lastb" command, create /var/log/btmp: # touch /var/log/btmp |